Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#561 YAML validation tests #691

Merged
merged 3 commits into from
Dec 29, 2014
Merged

#561 YAML validation tests #691

merged 3 commits into from
Dec 29, 2014

Conversation

krzyk
Copy link

@krzyk krzyk commented Dec 27, 2014

No description provided.

@krzyk
Copy link
Author

krzyk commented Dec 27, 2014

I've added wrong comment, this PR is actually for #570

@alex-palevsky
Copy link
Contributor

Thanks, I'll find someone to review this PR soon

@alex-palevsky
Copy link
Contributor

@longtimeago help us to review this

@longtimeago
Copy link

@krzyk Are you sure that all 3 phases (merge, deploy, release) are mandatory? I didn't found any doc about that

@yegor256
Copy link
Owner

@longtimeago @krzyk nothing is mandatory in the configuration. everything is optional.

@krzyk
Copy link
Author

krzyk commented Dec 29, 2014

@longtimeago I've changed the tests to fail if merge/deploy/release contains just a list instead of script and/or env element

@longtimeago
Copy link

@krzyk Now it looks good, thanks!

@longtimeago
Copy link

@rultor Please, merge

@rultor
Copy link
Collaborator

rultor commented Dec 29, 2014

@rultor Please, merge

@longtimeago Thanks for your request. @yegor256 Please confirm this.

@@ -16,6 +16,7 @@ architect:
install: |
sudo apt-get install bsdmainutils
sudo gem install pdd
sudo gem install kwalify
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what this is for? it's not used anywhere in the code below

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This just a help for the future implementer of todos, AFAIR rultor doesn't take into account .rultor.yml from PR during the build, just the one from master, has this changed?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's true, but once we merge this pull request, gem kwalify will be in master. Tasks/branches should be completely isolated. There is no guarantee that we will continue working on this problem after your pull request is merged. Maybe we will close the project right after. And the question will be - what this kwalify is doing here?

@yegor256
Copy link
Owner

@krzyk don't you think that this functionality is bloating GithubProfile? you see, you had to create a new test because of this. In general, it's a bad practice. Each Test.java file should map exactly to one .java file. So, this test is telling you that something is wrong with the design. I would suggest to create a new class ValidYaml

@krzyk
Copy link
Author

krzyk commented Dec 29, 2014

@yegor256 I was thinking of implementing validation in another class during the work on todo, as qualice will surely complain about the amount of classes/methods in GithubProfile.

@yegor256
Copy link
Owner

@krzyk but there is no guarantee that these TODO will be assigned to you. most probably they won't. and other developers won't know your ideas. so, either document your intention explicitly in TODO's or create a new ValidYaml class yourself. we should NOT keep anything in our heads between tasks. once you complete a task, you should forget everything you knew about it. all knowledge should stay in the source code.

@krzyk
Copy link
Author

krzyk commented Dec 29, 2014

@yegor256 please see the update

@yegor256
Copy link
Owner

@rultor good to merge

@rultor
Copy link
Collaborator

rultor commented Dec 29, 2014

@rultor good to merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor rultor merged commit 010def8 into yegor256:master Dec 29, 2014
@rultor
Copy link
Collaborator

rultor commented Dec 29, 2014

@rultor good to merge

@yegor256 Done! FYI, the full log is here (took me 13min)

@alex-palevsky
Copy link
Contributor

@longtimeago 30 mins sent to your balance (ID 49695331), many thanks!

@alex-palevsky
Copy link
Contributor

@rultor deploy

@rultor
Copy link
Collaborator

rultor commented Dec 31, 2014

@rultor deploy

@alex-palevsky OK, I'll try to deploy now. You can check the progress here

@rultor
Copy link
Collaborator

rultor commented Dec 31, 2014

@rultor deploy

@alex-palevsky Done! FYI, the full log is here (took me 8min)

@krzyk krzyk deleted the 561 branch October 10, 2015 12:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants